feat: support slowing down tests to enable debugging consequences #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change introduces a supported environment variable called `JUSTEST_SLOW_FACTOR` which, when set to an integer value, will cause Justest to multiple durations passed to the `For(...)` and `Within(...)` methods with its value. This will cause these duration to be longer, thus allowing the developer to investigate or debug side consequences of such tests - like logging into clusters and checking the effects of end-to-end tests, inspecting file-systems, etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces a supported environment variable called
JUSTEST_SLOW_FACTORwhich, when set to an integer value, will cause Justest to multiple durations passed to theFor(...)andWithin(...)methods with its value.This will cause these duration to be longer, thus allowing the developer to investigate or debug side consequences of such tests - like logging into clusters and checking the effects of end-to-end tests, inspecting file-systems, etc.